Dear All:

        We do Exchange 2013 Hyrbid.  We cannot migrate mailboxes from Office 365 to On-Premise but we can migrate mailboxes from On-premise to Office 365.  We get the below error.

EmailAddress,ErrorMessage
XXXXXXXX@XXXX.xxx,"Error: The call to 'https://xxxx.xxxx.xxxxx/EWS/mrsproxy.svc xxxx.xxx.xxx (15.0.1104.4 caps:1F7FFFFFCB07FFFF)' failed. Error details: Required property is missing. IsGroupFound=True, DisplayNameFound=False, SecurityIdentifierFound=True. --> Required property is missing. IsGroupFound=True, DisplayNameFound=False, SecurityIdentifierFound=True"

Please help me.  Thank you in advance.

Thanks,

Vith.

Hi,

I have logged a case for exactly this problem, exact same error message. It started happening just this week and ALL move requests are effected.

Brent

Same issue with us which started middle of last week

We are running Exchange 2013 CU5 - open case with Microsoft Premier support at the moment too.

Exact problem here also running 2013CU8, only happens on moves from cloud to onprem.
Last successful cloud->onprem move was on 09.July, first failure happened on 11.July

FailureCode                            : -2146233088
FailureType                            : CommunicationErrorTransientException
FailureSide                            : Target
Message                                : Error: The call to 'https://xxxxxxxxx/EWS/mrsproxy.svc xxxxxxxxx (1
                                         5.0.1076.6 caps:1F7FFFFFCB07FFFF)' failed. Error details: Required property is missing. IsGroupFound=True, DisplayNameFound=False, SecurityIdentifierFound=True. --> Required property is missing. IsGroupFound=True, DisplayNameFound=False, SecurityIdentifierFound=True

Did anybody ever get a fix for this. Got the same problem as well.

Call logged with Office 365 support

I haven't had any response from Microsoft (my support agent hasn't responded since finding this thread)

I was able to complete a single migration of a mailbox last night, the migration batch was initially setup in June.

Any luck with the deletion process? I've tried similar - although not all the migrations that are in the backend, just from the O365 Portal.

I've been told by Premier Support that it is a known bug and is now with the Product Support Team who are working on it.

I'll keep you posted - but brentos - would be good to know if deleting all backend migrations fixes it too.

Any luck with the deletion process? I've tried similar - although not all the migrations that are in the backend, just from the O365 Portal.

I've been told by Premier Support that it is a known bug and is now with the Product Support Team who are working on it.

I'll keep you posted - but brentos - would be good to know if deleting all backend migrations fixes it too.

I remove the failed move-requests and now, about half of the previously failed did complete.

After going through the failed and successful moverequests it seems the mail replication service in Office 365 needs an update.

Eg. one of the moves that now did complete did so after the Office 365 MRS had been updated from 15.1.219.7 to 15.1.219.17, and similary another mailbox completed after the MRS went from 15.1.213.13 to 15.1.213.21.

Other mailbox still on the same MRS versions failed as before.

Going to wait this out alittle and retry some more next week instead.

Get-OrganizationConfig| ft AdminDisplayVersion,IsUpgradingOrganization

We are on 15.1.213.21

However, looking at move request that I've restarted it is showing as the Server we are using as 15.1.213.13 so that mismatch might be causing us the pain?

• Edited by Andrew Specterman 6 hours 51 minutes ago

Hi,

2 out of 4 of migrations in my batch completed in the new batch yesterday. (It was really frustrating because it was 1 shared mailbox and 1 user the other 2 users were left isolated. ) However, I rerun the 'Complete this Batch' option this morning and 1 of the migrations completed. I now have just 1 user who cannot be completed in that batch.

I created a 2nd batch and the 2 out of 3 migrations completed overnight. Again rerunning the 'complete this batch' for this 2nd batch completed the last user.

I have created a 3rd batch with 12 users and this batch (set to auto complete) seems to be completing as expected.

My case has also been escalated to the premier support team, hopefully they can fix my 1 outstanding migration.

Brent

Get-OrganizationConfig| ft AdminDisplayVersion,IsUpgradingOrganization

We are on 15.1.213.21

However, looking at move request that I've restarted it is showing as the Server we are using as 15.1.213.13 so that mismatch might be causing us the pain?

• Edited by Andrew Specterman Friday, July 17, 2015 12:38 AM

Get-OrganizationConfig| ft AdminDisplayVersion,IsUpgradingOrganization

We are on 15.1.213.21

However, looking at move request that I've restarted it is showing as the Server we are using as 15.1.213.13 so that mismatch might be causing us the pain?

• Edited by Andrew Specterman Friday, July 17, 2015 12:38 AM

Similar situation here

2 out of 5 moves happened without issue - the other 3 still had the usual failures.

Retrying those again to see if they now work.

I've had confirmation from our Premier Support that the issues have been resolved

You'll need to ensure you are on at least 15.1.213.16 version of Office 365

We're now on 213.21 and 219.17 and offboarding moves have all been working

Andrew

I've had confirmation from our Premier Support that the issues have been resolved

You'll need to ensure you are on at least 15.1.213.16 version of Office 365

We're now on 213.21 and 219.17 and offboarding moves have all been working

Andrew

• Marked as answer by VithVith 4 hours 58 minutes ago

I've had confirmation from our Premier Support that the issues have been resolved

You'll need to ensure you are on at least 15.1.213.16 version of Office 365

We're now on 213.21 and 219.17 and offboarding moves have all been working

Andrew

• Marked as answer by VithVith Sunday, July 26, 2015 2:28 AM

Dear All

         As Andrew said, Microsoft has solved the problem, so now I can migrate mailboxes from O365 to On-premise.

         By the way, my tenant is 15.1.231.11.

Thanks,

Vith

• Marked as answer by VithVith 4 hours 58 minutes ago

Dear All

         As Andrew said, Microsoft has solved the problem, so now I can migrate mailboxes from O365 to On-premise.

         By the way, my tenant is 15.1.231.11.

Thanks,

Vith

• Marked as answer by VithVith Sunday, July 26, 2015 2:28 AM